<listitem>
<para>
-GtkAcceleratorTable has been replaced with GtkAccelGroup.
+<structname>GtkAcceleratorTable</structname> has been replaced with
+<structname>GtkAccelGroup</structname>.
</para>
</listitem>
<listitem>
<para>
-GtkMenuFactory has been replaced with GtkItemFactory, although
-a version of GtkMenuFactory is currently still provided to ease
-the migration phase.
+<structname>GtkMenuFactory</structname> has been replaced with
+<structname>GtkItemFactory</structname>, although
+a version of <structname>GtkMenuFactory</structname> is currently still
+provided to ease the migration phase.
</para>
</listitem>
<listitem>
<para>
-The GtkTypeInfo structures used in the gtk_*_type_init() functions have
+The <stuctname>GtkTypeInfo</structname> structures used in the
+<function>gtk_*_type_init()</function> functions have
changed a bit, the old format:
<programlisting>
GtkTypeInfo bin_info =
};
</programlisting>
- the GtkArgSetFunc and GtkArgGetFunc functions are not supported from the
- type system anymore, and you should make sure that your code only fills
- in these fields with NULL and doesn't use the deprecated function typedefs
- (GtkArgSetFunc) and (GtkArgGetFunc) anymore.
+ the <function>GtkArgSetFunc</function> and <function>GtkArgGetFunc</function>
+ functions are not supported from the type system anymore, and you should make
+ sure that your code only fills in these fields with <literal>NULL</literal>
+ and doesn't use the deprecated function typedefs
+ <literal>(GtkArgSetFunc)</literal> and <literal>(GtkArgGetFunc)</literal>
+ anymore.
</para>
</listitem>
<listitem>
<para>
-A number of Gtk functions were renamed. For compatibility, gtkcompat.h
- #define's the old 1.0.x function names in terms of the new names.
- To assure your Gtk program doesn't rely on outdated function
- variants, compile your program with -DGTK_DISABLE_COMPAT_H to disable
+A number of GTK+ functions were renamed. For compatibility,
+ <filename>gtkcompat.h</filename> #define's the old 1.0.x function names in
+ terms of the new names. To assure your GTK+ program doesn't rely on outdated
+ function variants, compile your program with
+ <option>-DGTK_DISABLE_COMPAT_H</option> to disable
the compatibility aliases.
Here is the list of the old names and replacements:
gtk_window_position gtk_window_set_position
(1) gtk_style_apply_default_background() has an additional
- argument, gboolean set_bg. This parameter should be FALSE if
- the background is being set for a NO_WINDOW widget, otherwise
- true.
+ argument, gboolean set_bg. This parameter should be
+ <literal>FALSE</literal> if the background is being set for a
+ NO_WINDOW widget, otherwise <literal>TRUE</literal>.
</programlisting>
</para>
</listitem>
<listitem>
<para>
-During the development phase of the 1.1.x line of Gtk certain functions
+During the development phase of the 1.1.x line of GTK+ certain functions
were deprecated and later removed. Functions affected are:
<programlisting>
<listitem>
<para>
-Additionally, all gtk_*_interp functions were removed.
- gtk_*_full versions were provided as of GTK+-1.0 and should
- be used instead.
+Additionally, all <function>gtk_*_interp()</function> functions were removed.
+ <function>gtk_*_full()</function> versions were provided as of GTK+ 1.0 and
+ should be used instead.
</para>
</listitem>
<listitem>
<para>
-GtkButton has been changed to derive from GtkBin.
- To access a button's child, use GTK_BIN (button)->child, instead
- of the old GTK_BUTTON (button)->child.
+<structname>GtkButton</structname> has been changed to derive from
+<structname>GtkBin</structname>.
+ To access a button's child, use <literal>GTK_BIN (button)->child</literal>,
+ instead of the old <literal>GTK_BUTTON (button)->child</literal>.
</para>
</listitem>
<para>
The selection API has been slightly modified:
- gtk_selection_add_handler() and gtk_selection_add_handler_full()
- have been removed. To supply the selection, one now register
+ <function>gtk_selection_add_handler()</function> and
+ <function>gtk_selection_add_handler_full()</function>
+ have been removed. To supply the selection, one now registers
the targets one is interested in with:
<programlisting>
<programlisting>
- To set a shape for a window, you must use
- gtk_widget_shape_combine_mask() instead of
- gdk_window_shape_combine_mask(), or the shape will be
+ <function>gtk_widget_shape_combine_mask()</function> instead of
+ <function>gdk_window_shape_combine_mask()</function>, or the shape will be
reset when switching themes.
- It is no longer permissable to draw directly on an arbitrary
widget, or to set an arbitrary widget's background pixmap.
- If you need to do that, use a GtkDrawingArea or (for a
- toplevel) a GtkWindow where gtk_widget_set_app_paintable()
+ If you need to do that, use a <structname>GtkDrawingArea</structname> or
+ (for a toplevel) a <structname>GtkWindow</structname> where
+ <function>gtk_widget_set_app_paintable()</function>
has been called.
</programlisting>
</para>
<listitem>
<para>
-The ScrolledWindow widget no longer creates a Viewport
- automatically. Instead, it has been generalized to accept
- any "self-scrolling" widget.
+The <structname>GtkScrolledWindow</structname> widget no longer creates a
+ <structname>GtkViewport</structname> automatically. Instead, it has been
+ generalized to accept any "self-scrolling" widget.
</para>
<para>
- The self-scrolling widgets in the Gtk+ core are GtkViewport,
- GtkCList, GtkCTree, GtkText, and GtkLayout. All of these widgets can
- be added to a scrolled window as normal children with
- gtk_container_add() and scrollbars will be set up automatically.
+ The self-scrolling widgets in the GTK+ core are
+ <structname>GtkViewport</structname>,
+ <structname>GtkCList</structname>, <structname>GtkCTree</structname>,
+ <structname>GtkText</structname>, and <structname>GtkLayout</structname>.
+ All of these widgets can be added to a scrolled window as normal children with
+ <function>gtk_container_add()</function> and scrollbars will be set up
+ automatically.
</para>
<para>
- To add scrollbars to a non self-scrolling widget, (such as a GtkList),
+ To add scrollbars to a non self-scrolling widget, (such as a
+ <function>GtkList</function>),
first add it to a viewport, then add the viewport to a scrolled window.
The scrolled window code provides a convenience function to do this:
GtkWidget *child);
</programlisting>
- This does exactly what it says - it creates a Viewport, adds the child
- widget to it, then adds the Viewport to the scrolled window.
+ This does exactly what it says - it creates a viewport, adds the child
+ widget to it, then adds the viewport to the scrolled window.
</para>
<para>
- The scrollbars have been removed from the GtkCList and GtkCTree,
- because they are now scrolled by simply adding them to a Scrolled
- Window. The scrollbar policy is set on the scrolled window with
- gtk_scrolled_window_set_policy() and not on the child widgets
- (e.g. GtkCList's gtk_clist_set_policy() was removed).
+ The scrollbars have been removed from the <structname>GtkCList</structname>
+ and <structname>GtkCTree</structname>, because they are now scrolled by simply
+ adding them to a scrolled window. The scrollbar policy is set on the scrolled
+ window with <function>gtk_scrolled_window_set_policy()</function> and not on
+ the child widgets (e.g. <structname>GtkCList</structname>'s
+ <function>gtk_clist_set_policy()</function> was removed).
</para>
</listitem>
<listitem>
<para>
-the GTK_BASIC flag was removed, and with it the corresponding
- macro and function GTK_WIDGET_BASIC() and gtk_widget_basic().
+the <literal>GTK_BASIC</literal> flag was removed, and with it the corresponding
+ macro and function <function>GTK_WIDGET_BASIC()</function> and
+ <function>gtk_widget_basic()</function>.
</para>
</listitem>
[...]
if (!frozen)
gtk_clist_thaw (clist);
+</programlisting>
it will not work anymore. It must be, simply:
+<programlisting>
gtk_clist_freeze (clist);
[...]
gtk_clist_thaw (clist);
<para>
This means:
-<programlisting>
- - You must call g_thread_init() before executing any
- other GTK+ or GDK functions in a threaded GTK+ program.
-
- - Idles, timeouts, and input functions are executed outside
- of the main GTK+ lock. So, if you need to call GTK+
- inside of such a callback, you must surround the callback
- with a gdk_threads_enter()/gdk_threads_leave() pair.
-
- [ However, signals are still executed within the main
- GTK+ lock ]
-
- In particular, this means, if you are writing widgets
- that might be used in threaded programs, you _must_
- surround timeouts and idle functions in this matter.
-
- As always, you must also surround any calls to GTK+
- not made within a signal handler with a
- gdk_threads_enter()/gdk_threads_leave() pair.
-
- - There is no longer a special --with-threads configure
- option for GTK+. To use threads in a GTK+ program, you
- must:
-
- a) If you want to use the native thread implementation,
- make sure GLib found this in configuration, otherwise,
- call you must provide a thread implementation to
- g_thread_init().
-
- b) Link with the libraries returned by:
+<itemizedlist>
+ <listitem>
+ <para>You must call <function>g_thread_init()</function> before
+ executing any other GTK+ or GDK functions in a threaded GTK+ program.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Idles, timeouts, and input functions are executed outside
+ of the main GTK+ lock. So, if you need to call GTK+
+ inside of such a callback, you must surround the callback
+ with a <function>gdk_threads_enter()</function>/<function>gdk_threads_leave()</function>
+ pair.
+ </para>
+
+ <para>However, signals are still executed within the main
+ GTK+ lock.
+ </para>
+
+ <para>In particular, this means, if you are writing widgets
+ that might be used in threaded programs, you _must_
+ surround timeouts and idle functions in this matter.
+ </para>
+
+ <para>As always, you must also surround any calls to GTK+
+ not made within a signal handler with a
+ <function>gdk_threads_enter()</function>/<function>gdk_threads_leave()</function>
+ pair.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>There is no longer a special <option>--with-threads</option>
+ <command>configure</command> option for GTK+. To use threads in a GTK+
+ program, you must:
+
+ <orderedlist>
+ <listitem>
+ <para>If you want to use the native thread implementation,
+ make sure GLib found this in configuration, otherwise,
+ call you must provide a thread implementation to
+ <function>g_thread_init()</function>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Link with the libraries returned by:
- gtk-config --libs gthread
-
- and use the cflags from:
-
- gtk-config --cflags gthread
-
- You can get these CFLAGS and LIBS by passing gthread
- as the fourth parameter to the AM_PATH_GTK automake
- macro.
-</programlisting>
+ <command>gtk-config --libs gthread</command>
+
+ and use the cflags from:
+
+ <command>gtk-config --cflags gthread</command>
+
+ You can get these <envar>CFLAGS</envar> and <envar>LIBS</envar> by
+ passing <literal>gthread</literal> as the fourth parameter to the
+ <literal>AM_PATH_GTK</literal> <application>automake</application>
+ macro.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
</para>
</listitem>
<listitem>
<para>
-Prior to GTK+-1.2, there were two conflicting interpretations
- of widget->requistion. It was either taken to be
- the size that the widget requested, or that size
- modified by calls to gtk_widget_set_usize(). In GTK+-1.2,
+Prior to GTK+ 1.2, there were two conflicting interpretations
+ of <literal>widget->requisition</literal>. It was either taken to be
+ the size that the widget requested, or that size modified by calls to
+ <function>gtk_widget_set_usize()</function>. In GTK+ 1.2,
it is always interpreted the first way.
</para>
<para>
Container widgets are affected in two ways by this:
-<programlisting>
- 1) Container widgets should not pass widget->requisition
- as the second parameter to gtk_widget_size_request().
- Instead they should call it like:
-
- GtkRequisition child_requisition;
- gtk_widget_size_request (widget, &child_requisition);
-
- 2) Container widgets should not access child->requisition
- directly. Either they should use the values returned
- by gtk_widget_size_request(), or they should call
- the new function:
-
+ <orderedlist>
+ <listitem>
+ <para>Container widgets should not pass
+ <literal>widget->requisition</literal> as the second parameter to
+ <function>gtk_widget_size_request()</function>.
+ Instead they should call it like:
+ <programlisting>
+ GtkRequisition child_requisition;
+ gtk_widget_size_request (widget, &child_requisition);
+ </programlisting>
+ </para>
+ </listitem>
+ <listitem>
+ <para>Container widgets should not access
+ <literal>child->requisition</literal> directly. Either they should use
+ the values returned by <function>gtk_widget_size_request()</function>,
+ or they should call the new function:
+ <programlisting>
void gtk_widget_get_child_requisition (GtkWidget *widget,
GtkRequisition *requisition);
-
- which returns the requisition of the given widget, modified
- by calls to gtk_widget_set_usize().
-</programlisting>
+ </programlisting>
+ which returns the requisition of the given widget, modified
+ by calls to <function>gtk_widget_set_usize()</function>.
+ </para>
+ </listitem>
+ </orderedlist>
</para>
</listitem>
<listitem>
<para>
-gtk_container_get_toplevels() was removed and replaced with
- gtk_window_list_toplevels(), which has different memory management
- on the return value (gtk_window_list_toplevels() copies the GList
- and also references each widget in the list, so you have to
- g_list_free() the list after first unref'ing each list member).
+<function>gtk_container_get_toplevels()</function> was removed and replaced
+ with <function>gtk_window_list_toplevels()</function>, which has different
+ memory management on the return value
+ (<function>gtk_window_list_toplevels()</function> copies the
+ <structname>GList</structname> and also references each widget in the list,
+ so you have to <function>g_list_free()</function> the list after first
+ unref'ing each list member).
</para>
</listitem>
<listitem>
<para>
-The gdk_time* functions have been removed. This functionality
- has been unused since the main loop was moved into GLib
+The <function>gdk_time*()</function> functions have been removed. This
+ functionality has been unused since the main loop was moved into GLib
prior to 1.2.
</para>
</listitem>
<listitem>
<para>
-The signature for GtkPrintFunc (used for gtk_item_factory_dump_items)
- has been changed to take a 'const gchar *' instead of 'gchar *', to
- match what we do for glib, and other similar cases.
+The signature for <function>GtkPrintFunc</function> (used for
+ <function>gtk_item_factory_dump_items()</function>)
+ has been changed to take a <type>const gchar *</type> instead of
+ <type>gchar *</type>, to match what we do for GLib, and other similar cases.
</para>
</listitem>
<listitem>
<para>
-The detail arguments in the GtkStyleClass structure are now 'const gchar *'.
+The detail arguments in the <structname>GtkStyleClass</structname> structure
+are now <type>const gchar *</type>.
</para>
</listitem>
<listitem>
<para>
-gtk_paned_set_gutter_size() has been removed, since the small handle tab
- has been changed to include the entire area previously occupied by
- the gutter.
+<function>gtk_paned_set_gutter_size()</function> has been removed, since the
+ small handle tab has been changed to include the entire area previously
+ occupied by the gutter.
</para>
</listitem>
<listitem>
<para>
-gtk_paned_set_handle_size() has been removed, in favor of a style property,
- since this is an option that only makes sense for themes to adjust.
+<function>gtk_paned_set_handle_size()</function> has been removed, in favor of
+ a style property, since this is an option that only makes sense for themes
+ to adjust.
</para>
</listitem>
<para>
GDK no longer selects OwnerGrabButtonMask for button presses. This means
that the automatic grab that occurs when the user presses a button
- will have owner_events = FALSE, so all events are redirected to the
- grab window, even events that would normally go to other windows of the
- window's owner.
+ will have <literal>owner_events = FALSE</literal>, so all events are
+ redirected to the grab window, even events that would normally go to
+ other windows of the window's owner.
</para>
</listitem>
<listitem>
<para>
-GtkColorSelectionDialog has now been moved into it's own set of files,
- gtkcolorseldialog.c and gtkcolorseldialog.h.
+<structname>GtkColorSelectionDialog</structname> has now been moved into it's
+ own set of files, <filename>gtkcolorseldialog.c</filename> and
+ <filename>gtkcolorseldialog.h</filename>.
</para>
</listitem>
<listitem>
<para>
-gtk_widget_shape_combine_mask() now keeps a reference count on the
- mask pixmap that is passed in.
+<function>gtk_widget_shape_combine_mask()</function> now keeps a reference
+ count on the mask pixmap that is passed in.
</para>
</listitem>
<listitem>
<para>
-The GtkPatternSpec has been moved to glib as GPatternSpec, the pattern
- arguments to gtk_item_factory_dump_items() and gtk_item_factory_dump_rc()
- have thusly been changed to take a GPatternSpec instead of GtkPatternSpec.
+The <structname>GtkPatternSpec</structname> has been moved to GLib as
+ <structname>GPatternSpec</structname>, the pattern
+ arguments to <function>gtk_item_factory_dump_items()</function> and
+ <function>gtk_item_factory_dump_rc()</function>
+ have thusly been changed to take a <structname>GPatternSpec</structname>
+ instead of a <structname>GtkPatternSpec</structname>.
</para>
</listitem>
<itemizedlist>
<listitem>
<para>
- GTK_TYPE_OBJECT is not a fundamental type anymore. Type checks of the
- style (GTK_FUNDAMENTAL_TYPE (some_type) == GTK_TYPE_OBJECT)
- will not work anymore. As a replacement, (GTK_TYPE_IS_OBJECT (some_type))
+ <literal>GTK_TYPE_OBJECT</literal> is not a fundamental type anymore. Type checks of the
+ style <literal>(GTK_FUNDAMENTAL_TYPE (some_type) == GTK_TYPE_OBJECT)</literal>
+ will not work anymore. As a replacement, <literal>(GTK_TYPE_IS_OBJECT (some_type))</literal>
can be used now.
</para>
</listitem>
<listitem>
<para>
-The following types vanished: GTK_TYPE_ARGS, GTK_TYPE_CALLBACK,
- GTK_TYPE_C_CALLBACK, GTK_TYPE_FOREIGN. The corresponding GtkArg
+The following types vanished: <literal>GTK_TYPE_ARGS</literal>, <literal>GTK_TYPE_CALLBACK</literal>,
+ <literal>GTK_TYPE_C_CALLBACK</literal>, <literal>GTK_TYPE_FOREIGN</literal>. The corresponding <structname>GtkArg</structname>
fields and field access macros are also gone.
</para>
</listitem>
<listitem>
<para>
-The following type aliases vanished: GTK_TYPE_FLAT_FIRST,
- GTK_TYPE_FLAT_LAST, GTK_TYPE_STRUCTURED_FIRST,
- GTK_TYPE_STRUCTURED_LAST.
+The following type aliases vanished: <literal>GTK_TYPE_FLAT_FIRST</literal>,
+ <literal>GTK_TYPE_FLAT_LAST</literal>, <literal>GTK_TYPE_STRUCTURED_FIRST</literal>,
+ <literal>GTK_TYPE_STRUCTURED_LAST</literal>.
</para>
</listitem>
<listitem>
<para>
-The type macros GTK_TYPE_MAKE() and GTK_TYPE_SEQNO() vanished, use of
- GTK_FUNDAMENTAL_TYPE() is discouraged. Instead, the corresponding GType
- API should be used: G_TYPE_FUNDAMENTAL(), G_TYPE_DERIVE_ID(),
- G_TYPE_BRANCH_SEQNO(). Note that the GLib type system doesn't build new
+The type macros <function>GTK_TYPE_MAKE()</function> and <function>GTK_TYPE_SEQNO()</function> vanished, use of
+ <function>GTK_FUNDAMENTAL_TYPE()</function> is discouraged. Instead, the corresponding <structname>GType</structname>
+ API should be used: <function>G_TYPE_FUNDAMENTAL()</function>, <function>G_TYPE_DERIVE_ID()</function>,
+ <function>G_TYPE_BRANCH_SEQNO()</function>. Note that the GLib type system doesn't build new
type ids based on a global incremental sequential number anymore, but
numbers new type ids sequentially per fundamental type branch.
</para>
<listitem>
<para>
Object system changes:
- GtkObject derives from GObject, so is not the basic object type anymore.
+ <structname>GtkObject</structname> derives from <structname>GObject</structname>, so is not the basic object type anymore.
This imposes the following source incompatible changes:
<itemizedlist>
<listitem>
<para>
-GtkObject has no klass field anymore, an object's class can be retrived
- with the object's coresponding GTK_<OBJECT>_GET_CLASS (object)
+<structname>GtkObject</structname> has no <literal>klass</literal> field anymore, an object's class can be retrieved
+ with the object's coresponding <literal>GTK_<OBJECT>_GET_CLASS (object)</literal>
macro.
</para>
</listitem>
<listitem>
<para>
-GtkObjectClass has no type field anymore, a class's type can be retrived
- with the GTK_CLASS_TYPE (class) macro.
+<structname>GtkObjectClass</structname> has no <literal>type</literal> field anymore, a class's type can be retrived
+ with the <literal>GTK_CLASS_TYPE (class)</literal> macro.
</para>
</listitem>
<listitem>
<para>
-GtkObjectClass does not introduce the finalize() and shutdown() methods
- anymore. While shutdown() is intended for GTK+ internal use only, finalize()
- is required by a variety of object implementations. GObjectClass.finalize
+<structname>GtkObjectClass</structname> does not introduce the <function>finalize()</function> and <function>shutdown()</function> methods
+ anymore. While <function>shutdown()</function> is intended for GTK+ internal use only, <function>finalize()</function>
+ is required by a variety of object implementations. <function>GObjectClass.finalize</function>
should be overriden here, e.g.:
<programlisting>
static void gtk_label_finalize (GObject *gobject)
Because the ::destroy signal can be emitted multiple times, it no longer
makes sense to check if a widget has been destroyed using the
- GTK_OBJECT_DESTROYED() macro, and this macro has been removed. If
- catching destruction is still needed, it can be done with a signal
- connection to ::destroy.
+ <function>GTK_OBJECT_DESTROYED()</function> macro, and this macro has been
+ removed. If catching destruction is still needed, it can be done with a
+ signal connection to ::destroy.
</para>
</listitem>
<listitem>
<para>
Signal system changes:
- The Gtk 2.0 signal merly proxies the GSignal system now.
- For future usage, direct use of the GSignal API is recommended,
- this avoids significant performance hits where GtkArg structures
- have to be converted into GValues. For language bindings,
- GSignal+GClosure provide a much more flexible and convenient
- mechanism to hook into signal emissions or install class default
- handlers, so the old GtkSignal API for language bindings is not
+ The GTK+ 2.0 signal system merely proxies the <structname>GSignal</structname
+ system now. For future usage, direct use of the
+ <structname>GSignal</structname> API is recommended,
+ this avoids significant performance hits where <structname>GtkArg</structname>
+ structures have to be converted into <structname>GValues</structname>. For
+ language bindings, <structname>GSignal</structname>+</structname>GClosure</structname>
+ provide a much more flexible and convenient mechanism to hook into signal
+ emissions or install class default handlers, so the old
+ <structname>GtkSignal</structname> API for language bindings is not
supported anymore.
</para>
<para>
- Functions that got removed in the Gtk signal API:
- gtk_signal_n_emissions(), gtk_signal_n_emissions_by_name(),
- gtk_signal_set_funcs(), gtk_signal_handler_pending_by_id(),
- gtk_signal_add_emission_hook(), gtk_signal_add_emission_hook_full(),
- gtk_signal_remove_emission_hook(), gtk_signal_query().
- Also, the GtkCallbackMarshal argument to gtk_signal_connect_full() is
+ Functions that got removed in the GTK+ signal API:
+ <function>gtk_signal_n_emissions()</function>,
+ <function>gtk_signal_n_emissions_by_name()</function>,
+ <function>gtk_signal_set_funcs()</function>,
+ <function>gtk_signal_handler_pending_by_id()</function>,
+ <function>gtk_signal_add_emission_hook()</function>,
+ <function>gtk_signal_add_emission_hook_full()</function>,
+ <function>gtk_signal_remove_emission_hook()</function>,
+ <function>gtk_signal_query()</function>.
+ Also, the <structname>GtkCallbackMarshal</structname> argument to
+ <function>gtk_signal_connect_full()</function> is
not supported anymore.
For many of the removed functions, similar variants are available
- in the g_signal_* namespace.
- The GSignal system perfomrs emissions in a slightly different manner than
- the old GtkSignal code. Signal handlers that are connected to signal "foo"
+ in the <function>g_signal_*</function> namespace.
+ The <structname>GSignal</structname> system performs emissions in a
+ slightly different manner than the old <structname>GtkSignal</structname>
+ code. Signal handlers that are connected to signal "foo"
on object "bar" while "foo" is being emitted, will not be called anymore
during the emission they were connected within.
</para>
<listitem>
<para>
-Inserting and deleting text in GtkEntry though functions such
- as gtk_entry_insert_text() now leave the cursor at its original
- position in the text instead of moving it to the location of
- the insertion/deletion.
+Inserting and deleting text in <structname>GtkEntry</structname> though
+ functions such as <function>gtk_entry_insert_text()</function> now leave
+ the cursor at its original position in the text instead of moving it to
+ the location of the insertion/deletion.
</para>
</listitem>
<listitem>
<para>
-The ->label field of GtkFrame widgets has been removed. (As part of
- a change to allow the arbitrary widgets in the title position.) The
- text can now be retrieved with the new function gtk_frame_get_text().
+The <literal>->label</literal> field of <structname>GtkFrame</structname>
+ widgets has been removed. (As part of a change to allow arbitrary widgets
+ in the title position.) The text can now be retrieved with the new function
+ <function>gtk_frame_get_text()</function>.
</para>
</listitem>
<listitem>
<para>
The 'font' and 'font_set' declarations in RC files are now ignored. There
- is a new 'font_name' field that holds the string form of a Pango font
+ is a new 'font_name' field that holds the string form of a Pango font.
</para>
</listitem>
<listitem>
<para>
-A number of types in GDK have become subclasses of GObject. For the
- most part, this should not break anyone's code. However, it's now
- possible/encouraged to use g_object_ref()/g_object_unref() and other
- GObject features with these GDK types. The converted types are:
- GdkWindow, GdkDrawable, GdkPixmap, GdkImage, GdkGC, GdkDragContext,
- GdkColormap
+A number of types in GDK have become subclasses of
+ <structname>GObject</structname>. For the most part, this should not break
+ anyone's code. However, it's now possible/encouraged to use
+ <function>g_object_ref()</function>/<function>g_object_unref()</function> and
+ other <structname>GObject</structname> features with these GDK types. The
+ converted types are:
+ <structname>GdkWindow</structname>, <structname>GdkDrawable</structname>,
+ <structname>GdkPixmap</structname>, <structname>GdkImage</structname>,
+ <structname>GdkGC</structname>, <structname>GdkDragContext</structname>,
+ <structname>GdkColormap</structname>.
</para>
</listitem>
<listitem>
<para>
All drawables including pixmaps used to have a type tag, the
- GdkWindowType enumeration, which included GDK_WINDOW_PIXMAP.
- GdkWindowType is now a property of GdkWindow
- <emphasis>only</emphasis>, and there is no GDK_WINDOW_PIXMAP. You
- can use the GDK_IS_PIXMAP() macro to see if you have a pixmap, if
+ <structname>GdkWindowType</structname> enumeration, which included
+ <literal>GDK_WINDOW_PIXMAP</literal>.
+ <structname>GdkWindowType</structname> is now a property of
+ <structname>GdkWindow</structname> <emphasis>only</emphasis>, and there is
+ no <literal>GDK_WINDOW_PIXMAP</literal>. You can use the
+ <function>GDK_IS_PIXMAP()</function> macro to see if you have a pixmap, if
you need to know that.
</para>
</listitem>
<listitem>
<para>
-GtkStyle and GtkRcStyle are now subclasses of GObject as well. This
+<structname>GtkStyle</structname> and <structname>GtkRcStyle</structname> are
+ now subclasses of <structname>GObject</structname> as well. This
requires fairly extensive changes to theme engines, but
shouldn't affect most other code.
</para>
<listitem>
<para>
-xthickness/ythickness have moved from GtkStyleClass to GtkStyle
+<literal>xthickness</literal>/</literal>ythickness</literal> have moved from
+ <structname>GtkStyleClass</structname> to <structname>GtkStyle</structname>
(from class to instance). This gives themes a bit more flexibility
and is generally more of the Right Thing. You can trivially fix
- your code with s/style->klass->xthickness/style->xthickness/g and
- same for ythickness.
+ your code with <literal>s/style->klass->xthickness/style->xthickness/g</literal> and
+ same for <literal>ythickness</literal>.
</para>
</listitem>
<listitem>
<para>
-Some GtkStyle draw_ methods have been removed (cross, oval, ramp)
+Some <structname>GtkStyle</structname> <function>draw_*()</function> methods
+ have been removed (cross, oval, ramp)
and others have been added (expander, layout). This will require
changes to theme engines.
</para>
<para>
The visual for a widget, and also the default visual is now derived
from the colormap for the widget and the default colormap.
- gtk_widget_set_visual(), gtk_widget_set_default_visual(),
- gtk_widget_push_visual() and gtk_widget_pop_visual() now do
+ <function>gtk_widget_set_visual()</function>,
+ <function>gtk_widget_set_default_visual()</function>,
+ <function>gtk_widget_push_visual()</function> and
+ <function>gtk_widget_pop_visual()</function> now do
nothing. Since the visual always had to match that of the colormap,
it is safe to simply delete all references to these functions.
</para>
<para>
A number of functions in GDK have been renamed for consistency and
clarity. #defines to provide backwards compatibility have been
- included, but can be disabled by defining GDK_DISABLE_DEPRECATED.
+ included, but can be disabled by defining <literal>GDK_DISABLE_DEPRECATED</literal>.
<programlisting>
#define gdk_draw_pixmap gdk_draw_drawable
#define gdk_rgb_get_cmap gdk_rgb_get_colormap
</programlisting>
- gtk_widget_popup() was removed, it was only usable for GtkWindows, and
- there the same effect can be achieved by gtk_window_move() and
- gtk_widget_show().
+ <function>gtk_widget_popup()</function> was removed, it was only usable
+ for <structname>GtkWindow</structname>s, and there the same effect can be
+ achieved by <function>gtk_window_move()</function> and
+ <function>gtk_widget_show()</function>.
</para>
</listitem>
<listitem>
<para>
-gdk_pixmap_foreign_new() no longer calls XFreePixmap() on the
- pixmap when the GdkPixmap is finalized. This change corresponds
- to the behavior of gdk_window_foreign_new(), and fixes a lot
- of problems with code where the pixmap wasn't supposed to be
- freed. If XFreePixmap() is needed, it can be done using the
- destroy-notification facilities of g_object_set_data().
+<function>gdk_pixmap_foreign_new()</function> no longer calls
+ <function>XFreePixmap()</function> on the pixmap when the
+ <structname>GdkPixmap</structname> is finalized. This change corresponds
+ to the behavior of <function>gdk_window_foreign_new()</function>, and fixes
+ a lot of problems with code where the pixmap wasn't supposed to be freed.
+ If <function>XFreePixmap()</function> is needed, it can be done using the
+ destroy-notification facilities of <function>g_object_set_data()</function>.
</para>
</listitem>
<listitem>
<para>
-GtkProgress/GtkProgressBar had serious problems in GTK 1.2.
+<structname>GtkProgress</structname>/<structname>GtkProgressBar</structname>
+ had serious problems in GTK+ 1.2.
<itemizedlist>
<listitem>
<para>
Only 3 or 4 functions are really needed for 95% of progress
- interfaces; GtkProgress[Bar] had about 25 functions, and
- didn't even include these 3 or 4.
+ interfaces; <structname>GtkProgress[Bar]</structname> had about 25
+ functions, and didn't even include these 3 or 4.
</para>
</listitem>
In activity mode, the API involves setting the adjustment
to any random value, just to have the side effect of
calling the progress bar update function - the adjustment
- is totally ignored in activity mode
+ is totally ignored in activity mode.
</para>
</listitem>
<para>
You set the activity step as a pixel value, which means to
set the activity step you basically need to connect to
- size_allocate
+ size_allocate.
</para>
</listitem>
<listitem>
<para>
-There are ctree_set_expander_style()-functions, to randomly
- change look-and-feel for no good reason
+There are <function>ctree_set_expander_style()</function>-functions, to
+ randomly change look-and-feel for no good reason.
</para>
</listitem>
<listitem>
<para>
-The split between GtkProgress and GtkProgressBar makes no sense
- to me whatsoever.
+The split between <structname>GtkProgress</structname> and
+<structname>GtkProgressBar</structname> makes no sense to me whatsoever.
</para>
</listitem>
</itemizedlist>
- This was a big wart on GTK and made people waste lots of time,
+ This was a big wart on GTK+ and made people waste lots of time,
both learning and using the interface.
So, we have added what we feel is the correct API, and marked all the
rest deprecated. However, the changes are 100% backward-compatible and
<listitem>
<para>
-The GtkNotebookPage structure has been removed from the public header files;
+The <structname>GtkNotebookPage</structname> structure has been removed from
+ the public header files;
this was never meant to be a public structure, and all functionality that
could be done by accessing the struct fields of this structure should be
- accesible otherwise.
+ accessible otherwise.
</para>
</listitem>
<listitem>
<para>
-GtkMenuPositionFunc has a new parameter push_in which controls how
- menus placed outside the screen is handled. If this is set to true and
- part of the menu is outside the screen then Gtk+ pushes it into the visible
+<function>GtkMenuPositionFunc</function> has a new parameter
+ <literal>push_in</literal> which controls how menus placed outside the
+ screen is handled. If this is set to <literal>TRUE</literal> and
+ part of the menu is outside the screen then GTK+ pushes it into the visible
area. Otherwise the menu is cut of at the end of the visible screen area.
</para>
<para>
- Regardles of what happens to the size of the menu, the result is always
+ Regardless of what happens to the size of the menu, the result is always
that the items are placed in the same place as if the menu was placed
outside the screen, using menu scrolling if necessary.
</para>
<listitem>
<para>
-The "draw" signal and virtual method on GtkWidget has been removed.
+The "draw" signal and virtual method on <structname>GtkWidget</structname>
+ has been removed.
All drawing should now occur by invalidating a region of the widget
- (call gdk_window_invalidate_rect() or gtk_widget_queue_draw() for
- example to invalidate a region). GTK+ merges all invalid regions,
- and sends expose events to the widget in an idle handler for the
- invalid regions. gtk_widget_draw() is deprecated but still works; it
+ (call <function>gdk_window_invalidate_rect()</function> or
+ <function>gtk_widget_queue_draw()</function> for example to invalidate
+ a region). GTK+ merges all invalid regions, and sends expose events to
+ the widget in an idle handler for the invalid regions.
+ <function>gtk_widget_draw()</function> is deprecated but still works; it
adds the passed-in area to the invalid region and immediately sends
expose events for the current invalid region.
Most widgets will work fine if you just delete their "draw"
<listitem>
<para>
-The GdkExposeEvent has a new region field. This can be used instead
- of the area field if you want a more exact representation of the
- area to update.
+The <structname>GdkExposeEvent</structname> has a new <literal>region</literal>
+ field. This can be used instead of the <literal>area</literal> field if you
+ want a more exact representation of the area to update.
</para>
</listitem>
<listitem>
<para>
-Sending synthetic exposes using gtk_widget_event is no longer allowed.
- If you just need an expose call you should use gdk_window_invalidate_rect()
- or gdk_window_invalidate_region() instead. For the case of container
- widgets that need to propagate expose events to NO_WINDOW children
- you can either use gtk_container_propagate_expose(), or chain to the
+Sending synthetic exposes using <function>gtk_widget_event()</function> is no
+ longer allowed. If you just need an expose call you should use
+ <function>gdk_window_invalidate_rect()</function> or
+ <function>gdk_window_invalidate_region()</function> instead. For the case
+ of container widgets that need to propagate expose events to
+ <literal>NO_WINDOW</literal> children you can either use
+ <function>gtk_container_propagate_expose()</function>, or chain to the
default container expose handler.
</para>
</listitem>
<listitem>
<para>
-The draw_default and draw_focus methods/signals on GtkWidget are
- gone; simply draw things in your expose handler.
- gtk_widget_draw_focus() and gtk_widget_draw_default() wrapper
+The draw_default and draw_focus methods/signals on
+ <structname>GtkWidget</structname> are gone; simply draw things in your
+ expose handler. <function>gtk_widget_draw_focus()</function> and
+ <function>gtk_widget_draw_default()</function> wrapper
functions are also gone; just queue a draw on the widget,
or the part affected by the focus/default anyway.
- Also, GtkWidget now has default implementations for focus_in_event
- and focus_out_event. These set/unset GTK_HAS_FOCUS, and queue a
- draw. So if your focus in/out handler just does that, you can delete
- it.
+ Also, <structname>GtkWidget</structname> now has default implementations for
+ focus_in_event and focus_out_event. These set/unset
+ <literal>GTK_HAS_FOCUS</literal>, and queue a draw. So if your focus in/out
+ handler just does that, you can delete it.
</para>
</listitem>
<listitem>
<para>
-GtkText and GtkTree are buggy and broken. We don't recommend using
- them, and changing old code to avoid them is a good idea. The
- recommended alternatives are GtkTextView and GtkTreeView. The
- broken widgets are not declared in the headers by default; to use
- them, define the symbol GTK_ENABLE_BROKEN during compilation. In
- some future release, these widgets will be removed from GTK+.
+<structname>GtkText</structname> and <structname>GtkTree</structname> are
+ buggy and broken. We don't recommend using them, and changing old code to
+ avoid them is a good idea. The recommended alternatives are
+ <structname>GtkTextView</structname> and <structname>GtkTreeView</structname>.
+ The broken widgets are not declared in the headers by default; to use
+ them, define the symbol <literal>GTK_ENABLE_BROKEN</literal> during
+ compilation. In some future release, these widgets will be removed from GTK+.
</para>
</listitem>
<listitem>
<para>
-GdkColorContext is gone; you probably weren't using it anyway.
- Use GdkColormap and the gdk_rgb_* functions instead.
+<structname>GdkColorContext</structname> is gone; you probably weren't using
+ it anyway. Use <structname>GdkColormap</structname> and the
+ <function>gdk_rgb_*</function> functions instead.
</para>
</listitem>
<listitem>
<para>
-GtkMenuBar now draws the GtkContainer::border_width space outside
- the frame, not inside the frame
+<structname>GtkMenuBar</structname> now draws the GtkContainer::border_width
+ space outside the frame, not inside the frame.
</para>
</listitem>
<listitem>
<para>
-In GTK 1.2, if an event handler returned TRUE it prevented
+In GTK+ 1.2, if an event handler returned <literal>TRUE</literal> it prevented
propagation of that event to parent widgets. That is, the
event signal would not be emitted on parent widgets. In
- GTK 2.0, if an event handler returns TRUE, the current signal
- emission on the current widget is immediately stopped. That is,
+ GTK+ 2.0, if an event handler returns <literal>TRUE</literal>, the current
+ signal emission on the current widget is immediately stopped. That is,
other callbacks connected to the signal will not be invoked.
</para>
</listitem>
<listitem>
<para>
-gtk_toolbar_new() no longer has arguments. This function
- was broken because the default GtkToolbarStyle (icons, text, both)
- is now a user preference, which is overridden when you call
- gtk_toolbar_set_style(). The constructor forced everyone to
- override the preference, which was undesirable. So to port
+<function>gtk_toolbar_new()</function> no longer has arguments. This function
+ was broken because the default <literal>GtkToolbarStyle</literal> (icons,
+ text, both) is now a user preference, which is overridden when you call
+ <function>gtk_toolbar_set_style()</function>. The constructor forced everyone
+ to override the preference, which was undesirable. So to port
your app, decide if you want to force the toolbar style
or conform to the user's global defaults; if you want to force
- it, call gtk_toolbar_set_style().
+ it, call <function>gtk_toolbar_set_style()</function>.
</para>
<para>
- The orientation arg was removed from toolbar_new() as well, just
- because it wasn't very useful and we were breaking the function
+ The orientation arg was removed from <function>gtk_toolbar_new()</function>
+ as well, just because it wasn't very useful and we were breaking the function
anyway so had an opportunity to lose it. Call
- gtk_toolbar_set_orientation() to set toolbar orientation.
+ <function>gtk_toolbar_set_orientation()</function> to set toolbar orientation.
</para>
</listitem>
<listitem>
<para>
-GtkRange/GtkScrollbar/GtkScale were rewritten; this means that most
+<structname>GtkRange</structname>/</structname>GtkScrollbar</structname>/<structname>GtkScale</structname> were rewritten; this means that most
theme engines won't draw them properly, and any custom subclasses of
these widgets will need a rewrite (though if you could figure out
- how to subclass the old version of GtkRange, you have our
- respect). Also, GtkTroughType is gone.
+ how to subclass the old version of <structname>GtkRange</structname>, you
+ have our respect). Also, <literal>GtkTroughType</literal> is gone.
</para>
</listitem>
<listitem>
<para>
-The GtkContainer::focus signal/virtualfunction and
- gtk_container_focus() call were replaced by
- GtkWidget::focus and gtk_widget_child_focus().
+The GtkContainer::focus signal/virtual function and
+ <function>gtk_container_focus()</function> call were replaced by
+ GtkWidget::focus and <function>gtk_widget_child_focus()</function>.
The semantics are the same, so you should be able to just
- replace "container_class->focus = mywidget_focus" with
- "widget_class->focus = mywidget_focus" and replace
- gtk_container_focus() calls with gtk_widget_child_focus() calls.
+ replace <literal>container_class->focus = mywidget_focus</literal> with
+ <literal>widget_class->focus = mywidget_focus</literal> and replace
+ <function>gtk_container_focus()</function> calls with
+ <function>gtk_widget_child_focus()</function> calls.
</para>
<para>
The purpose of this change was to allow non-containers to have
<listitem>
<para>
-gtk_rc_set_image_loader() and gtk_rc_load_image() has been removed, now
+<function>gtk_rc_set_image_loader()</function> and
+<function>gtk_rc_load_image()</function> have been removed, now
that GTK+ includes decent image loading capabilities itself.
</para>
</listitem>
<listitem>
<para>
-An extra GtkSettings argument has been added to
- gtk_rc_find_pixmap_in_path(). This function is only actually useful
- from a theme engine during parsing, at which point the GtkSettings
- is provided.
+An extra <structname>GtkSettings</structname> argument has been added to
+ <function>gtk_rc_find_pixmap_in_path()</function>. This function is only
+ actually useful from a theme engine during parsing, at which point the
+ <structname>GtkSettings</structname> is provided.
</para>
</listitem>
<listitem>
<para>
-The child argument facility in gtkcontainer.c has been converted
- to a child property facility using GParamSpec and other facilities
- for GObject.
+The child argument facility in <filename>gtkcontainer.c</filename> has been
+ converted to a child property facility using
+ <structname>GParamSpec</structname> and other facilities
+ for <structname>GObject</structname>.
</para>
</listitem>
<listitem>
<para>
-The set_child_arg and get_child_arg virtual methods have been
- replaced with set_child_property / get_child_property, which
+The <function>set_child_arg()</function> and <function>get_child_arg()</function>
+ virtual methods have been replaced with <function>set_child_property()</function>/<function>get_child_property()</function>, which
work similar to GObject->set_property/get_property.
</para>
</listitem>
<listitem>
<para>
-Other removed GtkContainer unctions with the replacements:
+Other removed <structname>GtkContainer</structname> functions with the replacements:
<programlisting>
gtk_container_add_child_arg_type => gtk_container_class_install_child_property
<listitem>
<para>
-gdk_image_get() (or rather its replacement,
- gdk_drawable_get_image()) now handles errors properly by returning
- NULL, previously it would crash. Also, a window being offscreen is
- no longer considered an error; instead, the area being contains
- undefined contents for the offscreen areas. In most cases, code
- using gdk_image_get() should really be ported to
- gdk_pixbuf_get_from_drawable().
+<function>gdk_image_get()</function> (or rather its replacement,
+ <function>gdk_drawable_get_image()</function>) now handles errors properly
+ by returning <literal>NULL</literal>, previously it would crash. Also, a
+ window being offscreen is no longer considered an error; instead, the area
+ contains undefined contents for the offscreen areas. In most cases, code
+ using <function>gdk_image_get()</function> should really be ported to
+ <function>gdk_pixbuf_get_from_drawable()</function>.
</para>
</listitem>
<listitem>
<para>
-gtk_widget_set_usize() has been renamed to
- gtk_widget_set_size_request(), however the old name still exists
- unless you define GTK_DISABLE_DEPRECATED.
+<function>gtk_widget_set_usize()</function> has been renamed to
+ <function>gtk_widget_set_size_request()</function>, however the old name
+ still exists unless you define <literal>GTK_DISABLE_DEPRECATED</literal>.
</para>
</listitem>
<listitem>
<para>
-gtk_widget_set_uposition() is deprecated; use gtk_window_move(),
- gtk_fixed_put(), or gtk_layout_put() instead.
+<function>gtk_widget_set_uposition()</function> is deprecated; use
+ <function>gtk_window_move()</function>,
+ <function>gtk_fixed_put()</function>, or <function>gtk_layout_put()</function>
+ instead.
</para>
</listitem>
<listitem>
<para>
-gtk_window_set_policy() is deprecated. To get the effect of
- "allow_shrink", call gtk_widget_set_size_request(window, 0, 0). To
- get the effect of "allow_grow", call
- gtk_window_set_resizable(window, TRUE). You didn't want the effect
- of auto_shrink, it made no sense. But maybe if you were using it you
- want to use gtk_window_resize (window, 1, 1) to snap a window back
- to its minimum size (the 1, 1 will be rounded up to the minimum
- window size).
+<function>gtk_window_set_policy()</function> is deprecated. To get the effect of
+ "allow_shrink", call
+ <literal>gtk_widget_set_size_request (window, 0, 0)</literal>. To get the
+ effect of "allow_grow", call
+ <literal>gtk_window_set_resizable (window, TRUE)</literal>. You didn't want
+ the effect of "auto_shrink", it made no sense. But maybe if you were using
+ it you want to use <literal>gtk_window_resize (window, 1, 1)</literal> to
+ snap a window back to its minimum size (the 1, 1 will be rounded up to the
+ minimum window size).
</para>
</listitem>
<para>
The core GTK+ now takes care of handling mapping, unmapping and
realizing the child widgets of containers in
- gtk_widget_set_parent(). In most cases, this allows container
- implementations to be simplifid by removing the code in add()
- methods to map and realize children. However, there are
- a couple of things to watch out for here:
+ <function>gtk_widget_set_parent()</function>. In most cases, this allows
+ container implementations to be simplified by removing the code in
+ <function>add()</function> methods to map and realize children. However,
+ there are a couple of things to watch out for here:
</para>
</listitem>
<listitem>
<para>
-If the parent is realized before the add() happens,
- gtk_widget_set_parent_window() must be called before
- gtk_widget_set_parent(), since gtk_widget_set_parent()
- will realize the child.
+If the parent is realized before the <function>add()</function> happens,
+ <function>gtk_widget_set_parent_window()</function> must be called before
+ <function>gtk_widget_set_parent()</function>, since
+ <function>gtk_widget_set_parent()</function> will realize the child.
</para>
</listitem>
<listitem>
<para>
If a container depended on its children not being mapped
- unless it did so itself (for example, GtkNotebook only
- mapped the current page), then the new function
- gtk_widget_set_child_visible() must be called to keep
+ unless it did so itself (for example, <structname>GtkNotebook</structname>
+ only mapped the current page), then the new function
+ <function>gtk_widget_set_child_visible()</function> must be called to keep
widgets that should not be mapped not mapped.
</para>
<para>
- As part of this change, most containers also will no longer need
- custom implementations of the map() and unmap() virtual
- functions. The only cases where this is necessary are:
+ As part of this change, most containers also will no longer need custom
+ implementations of the <function>map()</function> and
+ <function>unmap()</function> virtual functions. The only cases where this
+ is necessary are:
<itemizedlist>
<listitem>
<para>
-For !NO_WINDOW widgets, if you create children of widget->window
- and don't map them in realize() then you must map them
- in map(). [ In almost all cases, you can simply map the
- windows in realize() ]
+For <literal>!NO_WINDOW</literal> widgets, if you create children of
+ <literal>widget->window</literal>
+ and don't map them in <function>realize()</function> then you must map them
+ in <function>map()</function. [ In almost all cases, you can simply map the
+ windows in <function>realize()</function>. ]
</para>
</listitem>
<listitem>
<para>
-For NO_WINDOW widgets, if you create windows in your realize()
- method, you must map then in map() and unmap them in unmap().
+For <literal>NO_WINDOW</literal> widgets, if you create windows in your
+ <function>realize()</function> method, you must map then in
+ <function>map()</function> and unmap them in <function>unmap()</function>.
</para>
</listitem>
</itemizedlist>
<listitem>
<para>
-gtk_widget_set_default_style (), gtk_widget_push_style (),
- and gtk_widget_pop_style () have been removed, since they
+<function>gtk_widget_set_default_style()</function>,
+ <function>gtk_widget_push_style()</function>,
+ and <function>gtk_widget_pop_style()</function> have been removed, since they
did not work properly with themes and there were better
alternatives for modifying the appearance of widgets.
- You should generally use gtk_widget_modify_fg/bg/base/text/font
+ You should generally use <function>gtk_widget_modify_*()</function>
instead.
</para>
</listitem>
<listitem>
<para>
-gtk_image_new() now takes no arguments and creates an empty GtkImage
- widget. To create a GtkImage widget from a GdkImage (the least
- common usage of GdkImage), use gtk_image_new_from_image.
+<function>gtk_image_new()</function> now takes no arguments and creates an
+ empty <structname>GtkImage</structname> widget. To create a
+ <structname>GtkImage</structname> widget from a
+ <structname>GdkImage</structname> (the least
+ common usage of <structname>GdkImage</structname>), use
+ <function>gtk_image_new_from_image()</function>.
</para>
</listitem>
<listitem>
<para>
-GTK_SELECTION_EXTENDED is now deprecated, and neither the
- GtkList/GtkTree nor the GtkCList/GtkCTree support
- GTK_SELECTION_EXTENDED anymore. However, the old extended behavior
- replaces MULTIPLE behavior.
+<literal>GTK_SELECTION_EXTENDED</literal> is now deprecated, and neither the
+ <structname>GtkList</structname>/<structname>GtkTree</structname> nor the
+ <structname>GtkCList</structname>/<structname>GtkCTree</structname> support
+ <literal>GTK_SELECTION_EXTENDED</literal> anymore. However, the old extended
+ behavior replaces <literal>MULTIPLE</literal> behavior.
</para>
</listitem>
<programlisting>
Variable Replacement
======== ===========
- gdk_null_window_warnings None - did nothing in GTK+-1.2.
+ gdk_null_window_warnings None - did nothing in GTK+ 1.2.
gdk_leader_window None - private variable
gdk_screen gdk_x11_get_default_screen ()
gdk_root_window gdk_x11_get_default_root_xwindow ()
<listitem>
<para>
-The handling of Colormaps and widgets has been changed:
+The handling of colormaps and widgets has been changed:
<itemizedlist>
<listitem>
<para>
-The default colormap for widgets is now the GdkRGB colormap, not
- the system default colormap. If you try to use resources created for
- a widget (e.g., widget->style) with a window using the system
- colormap, errors will result on some machines.
+The default colormap for widgets is now the <structname>GdkRGB</structname>
+ colormap, not the system default colormap. If you try to use resources
+ created for a widget (e.g., <literal>widget->style</literal>) with
+ a window using the system colormap, errors will result on some machines.
</para>
</listitem>
<listitem>
<para>
-gtk_widget_push/pop_colormap() only cause the colormap to be
- explicitely set on toplevel widgets not on all widgets. The
- colormap for other widgets (when not set using
- gtk_widget_set_colormap()), is determined by finding the nearest
- ancestor with a colormap set on it explicitely, or if that
+<function>gtk_widget_push()</function>/<function>gtk_widget_pop_colormap()</function>
+ only cause the colormap to be explicitly set on toplevel widgets, not on
+ all widgets. The colormap for other widgets (when not set using
+ <function>gtk_widget_set_colormap()</function>), is determined by finding
+ the nearest ancestor with a colormap set on it explicitly, or if that
fails, the default colormap.
</para>
</listitem>
<listitem>
<para>
-The default selected day for GtkCalendar is now the current day in the
- month, not the first day in the month. The current month and year
- were already used.
+The default selected day for <structname>GtkCalendar</structname> is now the
+ current day in the month, not the first day in the month. The current month
+ and year were already used.
</para>
</listitem>
<listitem>
<para>
GDK is no longer put into threaded mode automatically when
- g_thread_init() has been called. In order to use the
- global GDK thread mutex with gdk_threads_enter() and
- gdk_threads_leave(), you must call gdk_threads_init() explicitely.
+ <function>g_thread_init()</function> has been called. In order to use the
+ global GDK thread mutex with <function>gdk_threads_enter()</function> and
+ <function>gdk_threads_leave()</function>, you must call
+ <function>gdk_threads_init()</function> explicitly.
If you aren't using GDK and GTK+ functions from multiple threads,
- there is no reason to call gdk_threads_init().
+ there is no reason to call <function>gdk_threads_init()</function>.
</para>
</listitem>
<listitem>
<para>
-The GtkPreviewInfo struct has had its visual and colormap fields
- removed. Also, gtk_preview_get_cmap() and gtk_preview_get_visual()
- are deprecated, as GdkRgb works on any colormap and visual. You no
- longer need to gtk_widget_push_cmap (gtk_preview_get_cmap ()) in
+The <structname>GtkPreviewInfo</structname> struct has had its visual and
+ colormap fields removed. Also, <function>gtk_preview_get_cmap()</function>
+ and <function>gtk_preview_get_visual()<function> are deprecated, as
+ <structname>GdkRGB</structname> works on any colormap and visual. You no
+ longer need to
+ <literal>gtk_widget_push_cmap (gtk_preview_get_cmap ())</literal> in
your code.
</para>
</listitem>
<listitem>
<para>
-The GtkBox, GtkTable, and GtkAlignment widgets now call
- gtk_widget_set_redraw_on_allocate (widget, FALSE); on themselves.
- If you want to actually draw contents in a widget derived from
+The <structname>GtkBox</structname>, <structname>GtkTable</structname>, and
+ <structname>GtkAlignment</structname> widgets now call
+ <literal>gtk_widget_set_redraw_on_allocate (widget, FALSE);</literal> on
+ themselves. If you want to actually draw contents in a widget derived from
one of these widgets, you'll probably want to change this
- in your init() function.
+ in your <function>init()</function> function.
</para>
</listitem>
<listitem>
<para>
-A number of widgets are now NO_WINDOW widgets (most importantly
- GtkButton, but also GtkRange and GtkNotebook)
+A number of widgets are now <literal>NO_WINDOW</literal> widgets (most
+ importantly <structname>GtkButton</structname>, but also
+ <structname>GtkRange</structname> and <structname>GtkNotebook</structname>)
This has a couple of effects:
<para>
If you are deriving from one of these widgets, you need to
adapt your code appropriately -- for instance, drawing coordinates
- start from widget->allocation.x, widget->allocation.y.
+ start from <literal>widget->allocation.x, widget->allocation.y</literal>.
</para>
</listitem>
<listitem>
<para>
If you are embedding one of these widgets in a custom widget,
- you must make sure you call gtk_container_propagate_expose()
- correctly, as you must for any NO_WINDOW widgets.
+ you must make sure you call <function>gtk_container_propagate_expose()</function>
+ correctly, as you must for any <literal>NO_WINDOW</literal> widgets.
</para>
</listitem>
</itemizedlist>
</para>
<para>
- GtkFixed is a little special; it is now created by default as
- a NO_WINDOW widget, but if you do
+ <structname>GtkFixed</structname> is a little special; it is now created by
+ default as a <literal>NO_WINDOW</literal> widget, but if you do
<programlisting>
gtk_fixed_set_has_window (fixed, TRUE);
<listitem>
<para>
-GtkLayout no longer has the xoffset, yoffset fields, which used
- to store the difference between world and window coordinates for
- layout->bin_window. These coordinate systems are now always
- the same.
+<structname>GtkLayout</structname> no longer has the <literal>xoffset</literal>,
+ <literal>yoffset</literal> fields, which used to store the difference between
+ world and window coordinates for <literal>layout->bin_window</literal>.
+ These coordinate systems are now always the same.
</para>
</listitem>
<listitem>
<para>
-gtk_paint_focus(), gtk_draw_focus() and GtkStyle::draw_focus()
+<function>gtk_paint_focus()</function>, <function>gtk_draw_focus()</function>
+ and <function>GtkStyle::draw_focus()</function>
have been changed a bit:
<itemizedlist>
<listitem>
<para>
-A GtkStateType argument has been added to gtk_paint_focus()
+A <literal>GtkStateType</literal> argument has been added to <function>gtk_paint_focus()</function>.
</para>
</listitem>
<listitem>
<para>
-The default implementation of GtkStyle::draw_focus virtual
- function now draws a focus rectangle whose width is
- determinted by the GtkWidget::focus-width style property.
+The default implementation of the <function>GtkStyle::draw_focus()</function>
+ virtual function now draws a focus rectangle whose width is
+ determined by the GtkWidget::focus-width style property.
</para>
</listitem>
<listitem>
<para>
The rectangle passed in is the bounding box, instead of
- the rectangle used in the gdk_draw_rectangle() call, so it is
- no longer necessary to subtract 1 from the width and height.
+ the rectangle used in the <function>gdk_draw_rectangle()</function> call,
+ so it is no longer necessary to subtract 1 from the width and height.
</para>
</listitem>
projects / gtk4.git / commitdiff